Remove obsolete Vercel deploy hook for docs-website#753
Merged
Conversation
The `update-docs-website` job in releaser.yml was a legacy of the pre-Renovate docs pipeline. Back then the docs-website pulled the Registry Server Swagger via jsdelivr (a remote reference), so every release needed Vercel to rebuild docs-website to pick up the new spec. This job triggered that rebuild. That path is retired. docs-website now pins the Swagger as a static file synced by `sync-assets.mjs` inside a Renovate-opened version- bump PR. Vercel auto-redeploys on push to the docs-website `main` branch when that PR merges. The hook currently fires after every release against docs-website `main` at a state where nothing has changed -- pure no-op that consumes runner minutes and creates a redundant deploy in Vercel. Noticed on the v1.3.0 release run: https://github.com/stacklok/toolhive-registry-server/actions/runs/24778037006/job/72503570856 The other three upstreams (`toolhive`, `toolhive-studio`, `toolhive-cloud-ui`) don't have an equivalent job -- `toolhive` was already cleaned up via stacklok/toolhive#4982 when the unified docs pipeline shipped. The `DOCS_VERCEL_DEPLOY_HOOK` repo secret can also be deleted once this merges, but left as a separate cleanup since I don't have secrets access.
ChrisJBurns
approved these changes
Apr 22, 2026
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #753 +/- ##
=======================================
Coverage 60.40% 60.40%
=======================================
Files 108 108
Lines 13041 13041
=======================================
Hits 7878 7878
Misses 4610 4610
Partials 553 553 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
The `update-docs-website` job in `releaser.yml` was a legacy of the pre-Renovate docs pipeline. Back then docs-website pulled the Registry Server Swagger via jsdelivr (a remote reference), so every release needed Vercel to rebuild docs-website to pick up the new spec. This job triggered that rebuild:
```yaml
update-docs-website:
name: Trigger Docs Website Rebuild
needs: [release-binaries]
runs-on: ubuntu-latest
steps:
- name: Trigger Vercel Deploy Hook
run: |
echo "Triggering docs website rebuild to refresh the API spec..."
curl -f -X POST "${{ secrets.DOCS_VERCEL_DEPLOY_HOOK }}" || exit 1
```
Why it's dead weight now
docs-website now pins the Swagger as a static file synced by `sync-assets.mjs` inside a Renovate-opened version-bump PR. Vercel auto-redeploys on push to docs-website's `main` branch when that PR merges.
The hook currently fires after every release against docs-website `main` at a state where nothing has changed — pure no-op that consumes runner minutes and creates a redundant deploy in Vercel.
Noticed on the v1.3.0 release run:
https://github.com/stacklok/toolhive-registry-server/actions/runs/24778037006/job/72503570856
Scope
Cross-checked the other three upstreams that docs-website tracks — `toolhive`, `toolhive-studio`, `toolhive-cloud-ui` — none have an equivalent job. `toolhive` was cleaned up via stacklok/toolhive#4982 when the unified docs pipeline shipped; this is the last leftover.
Follow-up (not in this PR)
The `DOCS_VERCEL_DEPLOY_HOOK` repo secret can be deleted once this merges — the only consumer is this job.